Common Terms
assembly: A reusable, versionable, and self-describing building block of a common language runtime application
domain: (From the Visual Studio .NET Help files) Application domains provide a secure and versatile unit of processing that the common language runtime can use to provide isolation between applications. You can run several application domains in a single process with the same level of isolation that would exist in separate processes, but without incurring the additional overhead of making cross-process calls or switching between processes. The ability to run multiple applications within a single process dramatically increases server scalability.
execution engine (EE): The common language runtime (CLR)
EEClass: A managed class.
EJIT (EconoJIT): An early JIT compiler, originally targetted at dynamic assemblies, ASP.NET pages and embedded script. This JIT compiler was optimized for compilation speed, but few optimizations were applied to the generated native code. Now of historical interest, it was not shipped with the .NET Framework.
field declarations (mdFieldDef): Declarations of data members as members of classes or interfaces or as global module-level data members.
HighFrequencyHeap:
LowFrequencyHeap:
mdToken:
A metadata token. A metadata token is a 4-byte value. The most-significant byte specifies what type of token this is. For example, a value of 1 indicates it’s a TypeDef token, and a value of 4 indicates it’s a FieldDef token. (For the full list of tokens and their values, see the CorTokenType enumeration in CorHdr.h) The lower three bytes give the index of the row, within a MetaData table, that the token refers to. These lower 3 bytes are called the RID, or Record IDentifier. So, for example, the metadata token with value 0x01000007 is a ‘shorthand’ way to refer to row number 7 in the TypeDef table, in the current scope. Similarly, token 0x0400001A refers to row number 26 (decimal) in the FieldDef table in the current scope. Nothing is ever stored in row zero of a metadata table: a a metadata token, whose RID is zero, is called a “nil” token. The metadata API defines a host of such nil tokens – one for each token type (for example, mdTypeDefNil, with value 0x01000000).member references (mdMemberRef): References to methods and fields. A member reference is generated in metadata for every method invocation or field access that is made by any implementation in this module and a token is persisted in the MSIL stream. (Note that there is no runtime support for property or event references)
MethodDesc. (MD):
method definitions (mdMethodDef): Definitions of methods as members of classes or interfaces or as global module-level methods.
MethodTable (MT):
Module:
Normal JIT: Used for normal operation; provides the best load/performance ratio. The load time of assemblies is a bit slower than using ngen'd assemblies, but the JIT compiler performs optimizations on the generated native code, taking into account, the current security policies and configuration.
ngen (formerly called Pre-JIT): Used for fast load time. This option is sometimes used for large local applications upon installation.
RVA (Relative Virtual Address): An RVA is the address of an item after it has been loaded into memory, with the base address of the image file subtracted from it (i.e. the offset from the base address where the file is loaded). The RVA of an item will almost always differ from its position within the file on disk.
StubHeap:
type declarations (mdTypeDef): Declarations of runtime reference types -- classes and interfaces – and of value types.
type references (mdTypeRef): References to runtime reference types and value types, such as might occur when declaring variables as runtime reference or value types or in declaring inheritance or implementation hierarchies. In a very real sense, the collection of type references in a module is the collection of compile-time import dependencies.